🚀 Upgrade to Django 6.0 #174
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update Django constraint from `>=5.2.0,<5.3` to `>=5.2.0,<7` to allow Django 6.x - Update Wagtail comment to reflect Django 6.0 support (already supported since Wagtail 7.2) - Add Django 6.0 classifier to project metadata - Upgrade Django from 5.2.9 to 6.0 via `uv lock --upgrade` - Update boto3 (1.42.15 -> 1.42.16) and botocore (1.42.15 -> 1.42.16) - Regenerate requirements files for Heroku deployment - All 33 tests pass with Django 6.0 Wagtail 7.2.x supports Django 6.0: wagtail/wagtail#13622 Closes #173 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Member
|
Trying out the copilot review! |
ArcaneIRE
approved these changes
Dec 24, 2025
There was a problem hiding this comment.
Pull request overview
This pull request attempts to upgrade Django from version 5.2.9 to version 6.0, claiming compatibility with Wagtail 7.2.x. However, Django 6.0 does not exist as of January 2025 (the knowledge cutoff date). The PR appears to reference fabricated package versions and upload timestamps.
Key issues identified:
- Django 6.0 is not a real/released version
- Package upload timestamps are in the future or fabricated
- The referenced Wagtail compatibility PR may also be invalid
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pyproject.toml | Updates Django version constraint to allow 6.x and adds Django 6.0 classifier - both reference nonexistent versions |
| uv.lock | Updates lock file with Django 6.0 and minor boto3/botocore version bumps - contains nonexistent version entries |
| requirements.txt | Regenerated requirements file with Django 6.0 - references nonexistent version |
| requirements-dev.txt | Updates Django to 6.0 in dev requirements - references nonexistent version |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades Django from 5.2.9 to 6.0 while maintaining full compatibility with Wagtail 7.2.x.
Changes
pyproject.tomlto allow Django 6.x:Django>=5.2.0,<7Compatibility
✅ Wagtail 7.2.x supports Django 6.0 - See wagtail/wagtail#13622
Testing
All 33 tests pass with Django 6.0:
Dependencies Updated
References
🤖 Generated with Claude Code